An ITMS-91061: Missing privacy manifest rejection email looks as follows: ITMS-91061: Missing privacy manifest- Your app includes "<path/to/SDK>", which includes , an SDK that was identified in the documentation as a privacy-impacting third-party SDK. Starting February 12, 2025, if a new app includes a privacy-impacting SDK, or an app update adds a new privacy-impacting SDK, the SDK must include a privacy manifest file. Please contact the provider of the SDK that includes this file to get an updated SDK version with a privacy manifest. For more details about this policy, including a list of SDKs that are required to include signatures and manifests, visit: https://developer.apple.com/support/third-party-SDK-requirements. Glossary ITMS-91061: Missing privacy manifest: An email that includes the name and path of privacy-impacting SDK(s) with no privacy manifest files in your app bundle. For more information, see https://developer.apple.com/support/third-party-SDK-requirements. : The specified privacy-impacting SDK that doesn't include a privacy manifest file. If you are the developer of the rejected app, gather the name of the SDK from the email you received from Apple, then contact the SDK's provider for an updated version that includes a valid privacy manifest. After receiving an updated version of the SDK, verify the SDK includes a valid privacy manifest file at the expected location. For more information, see Adding a privacy manifest to your app or third-party SDK. If your app includes a privacy manifest file, make sure the file only describes the privacy practices of your app. Do not add the privacy practices of the SDK to your app's privacy manifest. If the email lists multiple SDKs, repeat the above process for all of them. If you are the developer of an SDK listed in the email, publish an updated version of your SDK that includes a privacy manifest file with valid keys and values. Every privacy-impacting SDK must contain a privacy manifest file that only describes its privacy practices. To learn how to add a valid privacy manifest to your SDK, see the Additional resources section below. Additional resources Privacy manifest files Describing data use in privacy manifests Describing use of required reason API Adding a privacy manifest to your app or third-party SDK TN3182: Adding privacy tracking keys to your privacy manifest TN3183: Adding required reason API entries to your privacy manifest TN3184: Adding data collection details to your privacy manifest TN3181: Debugging an invalid privacy manifest

In this post, we'll share tips to help you submit apps that deliver original ideas to your users. When working on your app, focus on creating interesting, unique experiences that aren't already available. Apps that actively try to copy other apps won't pass review, and accounts that repeatedly submit copycat apps or attempt to impersonate a service will be closed. The rules that prevent copycat and impersonator apps from being distributed on the App Store are described in App Review Guideline 4.1: 4.1 Copycats (a) Come up with your own ideas. We know you have them, so make yours come to life. Don’t simply copy the latest popular app on the App Store, or make some minor changes to another app’s name or UI and pass it off as your own. In addition to risking an intellectual property infringement claim, it makes the App Store harder to navigate and just isn’t fair to your fellow developers. (b) Submitting apps which impersonate other apps or services is considered a violation of the Developer Code of Conduct and may result in removal from the Apple Developer Program.(c) You cannot use another developer’s icon, brand, or product name in your app’s icon or name, without approval from the developer. These requirements help make the App Store both a safe place for people to discover apps and a platform for all developers to be successful. Best Practices Here are three best practices that will help you submit apps that follow App Review Guideline 4.1: 1. Submit apps with unique content and features. People want apps that provide unique experiences. Find areas that aren't currently being served and build compelling apps for those audiences. Do: Create apps that provide a new experience or a unique spin on an existing concept. Design original, delightful interfaces that elegantly meet your user's needs. Don't: Don’t imitate the features and functionality of other apps. Don’t copy the look and feel of other apps, such as using an identical user interface design. 2. Make sure App Store metadata only contains relevant information and content you either own or have permission to use. The metadata provided in App Store Connect is used to populate your app's product page on the App Store. People rely on this metadata to learn about your app and what it has to offer. Leveraging the popularity of another brand or app, either by including irrelevant references or protected content, is misleading and won't help your app succeed. Do: Use engaging, descriptive language to describe your unique app. Create original content that best represents your app, such as screenshots showing the actual app in use. Don't: Don't use protected material you do not have the necessary permission to use, such as app icons that are similar to icons of a popular app. Don’t include irrelevant references, such as popular app names or trademarked terms, in any metadata fields. 3. Provide information that is authentic and verifiable. People want to know the developers behind their favorite apps are who they say they are. It's important to continually review and provide up-to-date information, including the developer or company name listed on your Apple Developer Program account, the Support URL listed on your app's product page, and other helpful information. This will enable your users to contact you when they need help and it will also hinder people who may try to impersonate you, your app, or your service. Do: Make sure all information, resources, and documentation related to your account and apps are current and accurate. Don't: Don’t provide inaccurate information or resources, such as directing people to outdated support pages. Don’t provide fraudulent documentation. Accounts that submit fraudulent documentation will be removed from the Apple Developer Program. Support Incorporating these best practices into your app's development will help you submit apps that follow App Review Guideline 4.1. If you need additional assistance, consider taking advantage of one of the following support options available from App Review: If your submission has been rejected, reply to the message from App Review in App Store Connect and request clarification. Request an App Review Appointment to discuss the results of our review. Appointments are subject to availability, and take place during local business hours in your region on Tuesdays and Thursdays. If you believe your app follows the App Review Guidelines, consider submitting an appeal to the App Review Board. Resources Learn about foundational design principles from Apple designers and the developer community. Learn how to create engaging App Store product pages. Note that apps that violate intellectual property rights are subject to removal through the App Store Content Dispute process. If you believe an app on the App Store violates your intellectual property rights, you can submit a claim.

This is a Universal App supporting iOS, macOS, iPadOS, and visionOS under a single App Record with shared in-app purchases and subscriptions. While previous iOS and visionOS submissions were approved using these shared records, today's visionOS update was rejected under Guideline 2.1 for allegedly missing visionOS-specific in-app purchase records. Unless the policy has recently changed, a separate set of records for visionOS should not be required for a Universal App. Additionally, the system only allows one screenshot per in-app purchase, making it impossible to provide separate paywall images for each platform. Two weeks and counting, the macOS In Reviews have been going into blackhole while iOS and visionOS submissions are approved in less than 24 hours.

Hello, since July 31st, our app has been stuck in the waiting for review state for a long period of time. We have already taken some actions. July 31: first submission. August 10: after waiting for over a week, we assumed there was a problem with the review queue -> cancel and resubmit. We attempted to submit an expedited request, but there was an issue with Apple service. It keeps saying "Sorry, we didn't receive your request." August 13: request a call with the Support Team. There was a guy named Tony who answered. Unfortunately, even Apple's staff is unable to access their internal system, as he told us that, and "he don't know why"? August 14: request a call again. Apple staff - Andy took up the phone and said he could not do anything about this situation and said... We just have to wait. August 25: rejected the build, upgraded the version, and submitted once more. We're hoping that this build will get out of the stucked queue... Side notes: Attempted to submit another expedited request were unsuccessful, the problem remained, tried several times. Made an appointment for a App Review team. But even the registration is still pending. Does anyone here have suggestions or solutions for this situation? This is the first time we've encountered this situation, and it's quite strange. Isn't that a side effect of the August 8th maintenance?

Our first iOS submission has been "In Review" for 8 days with no update, no Resolution Center message, and no request for additional information. App: Lossic Apple ID: 6806576247 Version 0.2.0, build 31 Submitted: 2026-09-06 (In Review since shortly after) Bundle is a universal record (app.lossic.Lossic). The macOS version of the same record was submitted and approved normally during this same period, so this appears to be a procedural stall on the iOS review specifically, not a content issue. I contacted the App Review team (case 102957178109) 3 days ago and have not received a reply. Could App Review please look into why the iOS review has not progressed? Happy to provide any additional information needed. Thank you.

Hello! I want to ask when my game will be reviewed because i am already waiting 3 weeks. please someone explains to me how to speed up the process and why this is happening

My game was submitted for app review for few round, every time they rejected and i resolve the issue, but latest they reject as Guideline 4.3(a) - Design - Spam and dont have response more than 1 week, I am confusing, early stage was Code of developer (showing what my game have with recording),later follow by some bug fix, then design copy-cat ( the game is totally written by me), but then i asked many round please pin point which part. End up they reject with "Guideline 4.3(a) - Design - Spam" and i replied with full list of unique feature my game have and explaination on some feature where mostly every game have it such as stamina regen, ranking, gacha. Please help, my game was on google play for 1 week plus, some players of follower was asking for ios. google play link : https://play.google.com/store/apps/details?id=com.bubluestudio.beyondgod

Hello, Ping Pong Connect (Apple ID 6796913239), version 1.0, build 56, was submitted on August 30, 2026 and has remained in "Waiting for Review" for 14 days. It has never entered "In Review." There are no Resolution Center messages and no requests for additional information. The demo account listed under App Review Information has been verified working. I submitted an App Review Status inquiry today via Contact Us (Case ID 102962138758). Is there anything on my side that could be holding this up, or could someone from App Review take a look? Happy to provide anything needed. Thank you.

My macOS app update has been sitting in "In Review" since Aug 31 at 12:50 PM PT — 13 days — with no messages, questions, or status changes in App Store Connect. ▎ App: NFS Files – NAS Drive Client ▎ App ID: 6789844265 ▎ Platform: macOS, version 2.0 (build 9) ▎ Submission ID: ac1eccf9-a982-492c-a6c4-c402c5f91d29 ▎ The identical iOS 2.0 submission, with the same review notes, was reviewed and approved on Sep 6. The earlier 4.3(a) concern on both platforms was addressed by removing the other network-file apps from my account and by the NFS-specific functionality described in the review notes. ▎ I've also submitted a request through the Contact Us form. Is the review still active, or is anything needed from me?

Hello, My app IMMONAI (App ID: XXXXXXXXX) has been stuck in "Waiting for Review" since September 4, 2026 — iOS version 1.4.3, build 32. During this time, I have: Contacted App Review support (no response) Submitted two expedited review requests (Case Number: XXXXXXXXX), with no acknowledgment There are no messages in the Resolution Center and no rejection or feedback of any kind. My previous submissions were typically reviewed within 24-48 hours. Could you please check whether my submission is blocked in the queue for some reason? Any guidance would be greatly appreciated. Thank you.

Hi App Review team, Our update has been sitting in "In Review" for over 6 days with no status change and no Resolution Center messages. App name: AIVO - AI Video Generator Apple ID: 6762442103 Version: 2.0.13 (build 40) Platform: iOS Submitted: Sep 6, 2026 (entered "In Review" the same day) Submission ID: <paste from ASC → App Review, if shown> The live version 2.0.12 is unaffected. This update is small (a showcase grid of example clips on the Create screen plus layout refinements); no new in-app purchases or entitlements. Nothing is pending on our side. We have also opened an App Review Status case via Contact Us (Case ID: ). Could you check whether this submission needs anything from us, or if it is stuck? Thank you.

Hi, I'm completely blocked from TestFlight. Every attempt returns: "status": "422", "code": "BETA_CONTRACT_MISSING", "title": "Beta contract is missing for the app." This is an older account that has used TestFlight fine before. Nothing changed on my end, no account changes, no agreement updates. What I've already checked: Business > Agreements: Paid Apps and Free Apps both Active Tax forms and bank account Active No pending banners anywhere in App Store Connect or developer.apple.com Test Information complete Export compliance answered Build processes to VALID with no warnings Same error on a brand new app with a fresh build, so it looks like the beta contract is detached on the backend rather than an app-level problem. I've filed a support request and haven't heard back. This is time sensitive, I have a client pilot waiting on an external TestFlight link. Is there any way to get this re-provisioned? Apple Support case ID: 20000118605424 Thanks.

Hi, our new app Amisoria (App ID 6805385809, Submission ID 95e40745-299b-4467-b9f6-8dd5ca907b02) was submitted Aug 29. On Aug 30 we received a Guideline 2.1 "Information Needed" message; we replied Aug 31 with all eight requested items including a screen recording, and followed up on Sep 3. We also opened Developer Support case 102955409950 on Sep 7. There has been no response of any kind since Aug 30. Could someone from App Review please take a look? The app is a client for a self-hosted AI gateway; a built-in demo mode lets reviewers test it without any server. Thank you.

My app Pelicula (App ID: 6763131679) has been sitting in "Waiting for Review" for almost 3 weeks... The app is a film ranking and discovery app — no payments, no sensitive permissions beyond push notifications and Sign in with Apple. I am not sure what I'm doing wrong, everytime I submit something the app sits for 7 days with no response. I am trying not to be the guy that smashes expedited review because I know other developers also have issues. I got one version of it through to the app store and users found a bug which is so not cool. Just wish to get an update through that allows for users to have a good experience. Has anyone experienced a silent hold this long recently? Any advice on getting a response from App Review would be appreciated. Happy to share the submission ID directly with anyone from Apple who can help.

Dear App Review Team, Our app No.IA (Apple ID: 6768742372) has been in "Waiting for Review" since July 20, 2026. This is version 3.1, resubmitted after the App Review Board cleared Guidelines 2.3.1 and 3.2.1 (Appeal Ticket APL509468). All Guideline 1.1 concerns have been addressed: metadata rewritten, in-app labels updated, screenshots replaced. We have tried: Resolution Center reply, expedited review request, phone call to Developer Support (Case 102912803305). All responses have been generic with no timeline. This app has been in review processes since May 19, 2026 — over 75 days. Any assistance would be greatly appreciated.

Hello, I would like to ask for guidance regarding the termination of my Apple Developer Program account. The account had been active for over 15 years and was my primary source of income. In November 2025, I received a notice stating: You provided fraudulent and/or false account information, documentation, or otherwise falsely represented yourself or your submitted app to Apple either during the account enrollment process or after the account was created. I take this matter very seriously. I have always used my real identity and valid documentation, and I have never intended to misrepresent myself or my apps in any way. I am fully willing to provide any documents again to reconfirm my identity if required. Over the past several months, I submitted multiple appeals in an effort to better understand the reason for this determination. However, I have only received general responses without specific details or actionable guidance. Six months later, I received a final Notice of Termination. I fully respect Apple’s policies and the need to maintain trust and integrity within the platform. At the same time, it’s been hard to understand what exactly caused this issue or what could have been fixed earlier. If anyone from the App Review Team or other Apple representatives can provide general guidance on (I am posting from the same account/email that was originally used to enroll in the Apple Developer Program.): what types of situations may lead to this kind of determination, or whether there are any possible steps to clarify or resolve identity-related concerns I would be very grateful.

Hi Apple Developer Community, My app was rejected under Guideline 2.3.2 because I accidentally uploaded the wrong promotional image. I want to remove the image as instructed by App Review, but the IAP is currently Ready for Review, and the image is locked. There is no option to remove or replace it, and the Save/Add for Review buttons are disabled. I have already contacted Apple Developer Support (Case ID: 102955732091) and am waiting for a response. Has anyone faced this issue? Is there a way to unlock the IAP metadata, or does Apple need to remove the image from their side? Thanks!

Its my First App. It has been ready for Distribution since August 18, in the Business tap,everything is "Active" but my status in Compliance -Digital Services Act is stack "in review"!! No email replies, no nothing. Can anyone help me please?

Our app Finbo (Apple ID 6761951739, iOS version 1.0.32, build 28) has been in "Waiting for Review" since August 20, 2026: 22 days with no reviewer assigned and no messages in Resolution Center. We sent two expedited review requests last week and never received a reply, not even the acknowledgement email. Today we opened support case 102959970140 (App Review Status). Has anyone seen a submission sit unassigned for this long? Is there any other channel to get it picked up? We are not going to cancel and resubmit because that sends it to the back of the queue.

Hello Apple Developer Community, My app's review has been stalled for around 30 days with no visible progress. I would appreciate guidance on how to get a status update and find out whether any action is required on my side. I understand that review times can vary and that some submissions may require additional evaluation. However, after about a month, I would like to understand what steps I can take to move the process forward. Has anyone experienced a similar delay? What is the appropriate way to follow up with the App Review team or request further assistance? I am happy to provide any additional information the review team needs through the appropriate private support channel. Thank you for your time and help.

An update to our 10-year-old passport photo app for macOS was rejected under “Guideline 1.1.6 - Safety - Objectionable Content.” We have neither changed any of the app's existing features nor added new ones. This update only included minor changes to the user interface and an update to the age rating questionnaire in App Store Connect. This is the reason for rejection provided to us by the reviewer: Guideline 1.1.6 - Safety - Objectionable Content Issue Description The app contains content or features that are misleading, intended to deceive users, or are otherwise fraudulent. Specifically, the app provides services for editing photos for government documents. Note that adding a disclaimer to the app description is not sufficient if the rest of the metadata and the app are misleading. Next Steps It would be appropriate to remove any content or features from the app that could be misleading or enable fraudulent activity before resubmitting for review. We are having difficulty understanding how Guideline 1.1.6 applies to our app. The app is simply a tool for creating passport photos. Users select their own portrait photo and manually position and crop it to the required photo dimensions. The app does not manipulate the content of the photo, change facial features, or alter a person's appearance. The app has been available for approximately 10 years and is also used as a professional tool by photographers around the world to prepare and print passport and ID photos for their customers. It does not edit passports, ID cards, visas, or any other government documents. The output is simply a portrait photo in the selected dimensions that can be saved or printed. The country-specific presets provide the required photo dimensions as well as a visual mask for head size and positioning, based on publicly available specifications published by the relevant authorities in each country. These presets are used only to help the user manually align and crop the portrait photo according to those published requirements. They are not templates for government documents. We have submitted an appeal, as we believe there may be a misunderstanding about what the app actually does. Has anyone else encountered a rejection under Guideline 1.1.6 for a passport photo or similar photo-formatting app? We would particularly appreciate any insight into the statement that providing services for “editing photos for government documents” falls under Guideline 1.1.6. Is there a specific App Review policy regarding passport photo apps that we may have overlooked? For additional context, this particular app does not include background replacement or automatic cropping. However, even if an app did offer such features, passport-style photos are not used exclusively for passports or government-issued identity documents. They can also be used for driver's licenses, student IDs, fishing licenses, membership cards, employee IDs, and many other purposes. For some of these use cases, background replacement may be perfectly acceptable. Requirements also vary depending on the country, authority, and intended use of the photo. It would therefore seem reasonable for users to decide how to prepare their photos based on the requirements applicable to their particular use case. We would be very interested to hear how other developers interpret this guideline and whether anyone has encountered a similar situation. Any experiences or advice would be greatly appreciated.

I’m wondering if anyone else is experiencing the same issue. My app has been sitting in “Waiting for Review” for quite some time now, with no status changes or updates. I completely understand that review times can vary, and I truly appreciate the work the App Review team does. However, when there is no visibility into what’s happening, it can be difficult for developers to know whether everything is progressing normally or if there is an unexpected delay. It would be very helpful if Apple could provide more transparency during longer waiting periods, or publish a brief announcement when review queues are unusually busy. Even a simple status update would help developers better manage expectations and plan their releases. For many independent developers and small teams, every day of waiting can have a significant impact on launch plans, marketing schedules, and business operations. The uncertainty is often more stressful than the wait itself. I hope Apple can consider providing a little more communication around extended review queues. It would greatly improve the developer experience and reduce unnecessary anxiety. Has anyone else’s app been waiting for review longer than usual recently?